-
Notifications
You must be signed in to change notification settings - Fork 168
docs: add getting started guide for EEST opcode minilang #1818
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@MozirDmitriy as-is, this is a drive-by PR that creates more work for us than if we'd done it ourselves. Can you read the issue, check the docs and put this somewhat in a relevant place? |
Yes, sorry, done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Please find a few comments below on how to link to the relevant data structures.
done |
Co-authored-by: danceratopz <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the drive on this one @MozirDmitriy gg!
docs/writing_tests/writing_a_new_test.md
with a small guide for using the Python-based EEST opcode minilang to write smart contracts in execution-spec-tests.Opcodes
class to generate bytecode, and described higher-level constructs such asSwitch
andCase
for advanced control flow.evm_bytes
CLI tool for converting EVM bytecode to the Python minilang.solc-select
dependency #1779).Fixes #1809